home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000139_icon-group-sender_Thu Nov 21 17:20:31 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id gAM0KTk13109
for icon-group-addresses; Thu, 21 Nov 2002 17:20:29 -0700 (MST)
Message-Id: <200211220020.gAM0KTk13109@baskerville.CS.Arizona.EDU>
From: jleger@afslogistics.com (Jonathan Leger)
X-Newsgroups: comp.lang.icon
Subject: Re: I know why Icon isn't popular.
Date: 21 Nov 2002 12:00:56 -0800
X-Complaints-To: groups-abuse@google.com
To: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Atle <trollet@skynet.be> wrote in message news:<3ddce97b$0$86562$ba620e4c@news.skynet.be>...
> If Icon became an 'IDE' language, it might initially attract some
> programmers, but the kind of programmers that you can find in the Visual
> Basic or Visual this-and-that world probably would not come to grips
> with such a powerful language anyway ...
>
> Atle
I must disagree with this. I am (professionally) a Visual Basic
programmer, but if given a choice I would love to be a professional
Icon programmer. I have been using Icon for years, and have certainly
"come to grips" with the language. Unfortunately there are no jobs
out there for Icon programmers.
I think that many programmers (such as myself) started with the Visual
this-and-that languages because that's what the market was looking
for, not because they are "easy." Though your statement may be true
for some, or maybe even most, it is certainly not true of all. I am
an example of that.
Jon